Skip to content

docs: add developer onboarding guide to CONTRIBUTING.md - #622

Open
woahwhattheheck wants to merge 9 commits into
Protocol-Guild:mainfrom
woahwhattheheck:wire/payd-561-contributing
Open

woahwhattheheck wants to merge 9 commits into
Protocol-Guild:mainfrom
woahwhattheheck:wire/payd-561-contributing

Conversation

@woahwhattheheck

Copy link
Copy Markdown

Closes #561

What

Replaces the three-line scaffold placeholder in CONTRIBUTING.md with a full contributor guide covering:

  • Architecture overview (frontend / backend / contracts / Stellar) with a simple diagram
  • Prerequisites and local setup for frontend, backend, and optional contracts
  • Environment and database configuration
  • Code style and standards (TypeScript/Rust, lint/format, typed errors, Apache-2.0)
  • Testing guide (Jest backend, Playwright frontend, Cargo contracts, CI expectations)
  • Pull request process and review criteria

Why

New contributors had no onboarding path beyond a leftover scaffold note. A real guide unblocks community setup and keeps PR quality consistent.

How tested

  • Manual review of the markdown against existing README, backend/.env.example, backend/frontend scripts, and .github/workflows/
  • Confirmed license guidance matches the Apache-2.0 LICENSE / Cargo workspace license

woahwhattheheck and others added 4 commits September 24, 2026 15:37
Replace the scaffold placeholder with setup instructions for frontend,
backend, and contracts, plus architecture overview, code standards,
testing guide, and PR process.

Closes Protocol-Guild#561
GitHub Actions does not accept retention-days on the workflow root.
That key is only valid on upload-artifact. The extra key made every
workflow fail validation on push before any job started.
GitHub Actions does not accept retention-days at the workflow root.
That made build, secrets-check, contract-release, and dapp-ipfs fail
with zero jobs on every push. Keep comments; set retention in repo settings.
Separate the frontend Vite command from the root Stellar scaffold watcher,
place frontend environment settings in its Vite project, and document one
PORT=3000 local API setting matching the existing frontend proxy and health URL.
Retain the backend's 3001 fallback when PORT is unset.

Refs Protocol-Guild#561. Validation: exact package-script, backend config, example-env,
frontend proxy, and Vite 7.2.6 root/envDir reconciliation; balanced Markdown
fences, resolved relative links, unchanged guide sections outside setup.
Docs only: no Node, application build/tests, or Prettier run during the
shared runtime-capacity hold. No runtime/configuration files changed.
Replace the malformed placeholder setup block with the real repository clone
command and links to the maintained prerequisites, setup, testing, and PR guide.
Keep the existing contributor guide and application source unchanged.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add CONTRIBUTING.md with developer onboarding guide

1 participant